-
Notifications
You must be signed in to change notification settings - Fork 839
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[maps] Azure Maps Track2 data-plane onboarding #15151
Conversation
This repository is protected by Check Enforcer. The check-enforcer check-run will not pass until there is at least one more check-run successfully passing. Check Enforcer supports the following comment commands:
|
Hi @ambientlight. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days. |
Hi @ambientlight. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing "/reopen" if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the "no-recent-activity" label; otherwise, this is likely to be closed again with the next cleanup pass. |
Initial onboarding of Azure Maps data-plane client libraries (9 clients) following Azure/azure-rest-api-specs#14871
SDK track2 autogen by https://github.com/ambientlight/azure-rest-api-specs/blob/experiment-scripts/gen_go.sh
This PR patches generated files
x-ms-client-id
header in addition to OAuth2 Bearer auth token, and so additional policy that adds this header to all requests has been injected into all clients via cd951cf and 049a823interface{}
via 981c73c, 71dd086, 23553ae